Table of Contents

Module: Transactions .\src\TW\Database\Transactions.py

Transaction Management, w/support for read-only vs. read-write transactions

This is just a thin shim over the normal Zope 2/ZPublisher/ZODB transaction interfaces, adding support for declaring a transaction pure read-only, or read-write. Read-write transactions must be explicitly declared, or they will not be allowed to make changes. Declaring a transaction read-only blocks it from being declared read-write. Transactions of unspecified mode can perform reads, but may lose data from their per-transaction caches if the transaction is later declared read-write (since highly volatile data may have been changed by another transaction, before the transaction was declared read-write).

It's not fully implemented yet, however. Notably, the flushing of cached volatile data is not yet supported.

Imported modules   
from TW.API import *
from TW.Caching import PermanentCache
from TW.Database.Interfaces import *
Classes   
TransactionManager

Track transaction count and mode

TransactionNotifier

Transaction boundary helper object

TransactionalCache

Clears cache on (sub-)transaction boundaries


Table of Contents

This document was automatically generated on Tue Mar 05 10:33:44 2002 by HappyDoc version WORKING